Pro Audio Spectrum 16 rev. D FAQ
December 1994

The following document contains 70 questions. Many of these are 
answered by Media Vision technicians on a daily basis. Be aware that this 
document is more than 30 printed pages long.

Media Vision is committed to providing  technical support.
Please feel free to contact us via any of the following methods.



Compuserve:	GO MEDIAVISION

BBS:		(510)  770 - 0527
		24 lines
		24 hr. / day
		14.4k baud and downward compatible
		Z - Modem recommended


Tech support 541-882-1177  or 900-555-1133  


If you need to contact Technical Support, please have 
the following information ready:

Customer ID #__________
The ID # is provided to you during your first call.

Multimedia Product purchased
Date of purchase
Name and version of Multimedia Software installation disk
Type of computer (386, 486, etc.)
Operating system and version (MSDOS, PCDOS, OS/2)
Memory (RAM) installed (2 MB, 4 MB, etc.)

Other devices in your system and their IRQ, DMA, and I/O addresses
if relevant to the problem or call.
Bus mouse
Scanner
Sound Card
CD-ROM drive
Fax/modem
Game card
MIDI device
Video Capture card
Other


1. WHICH ARE VALID DMA CHANNELS?
2. WHICH ARE VALID IRQ CHANNELS?
3. WHICH COMPUTERS WILL THE PRO AUDIO SPECTRUM 16 WORK IN?
4. HOW MUCH DISK SPACE IS REQUIRED FOR LOADING ALL THE FILES ON THE HARD
DRIVE?
5. CAN I HAVE TWO SOUND CARDS IN MY COMPUTER?
6. MY SYSTEM FILES ARE NOT BEING UPDATED AFTER I RUN THE INSTALLATION
PROGRAM.  HOW DO I FIX THIS?
7. WHAT CHANGES ARE MADE TO MY SYSTEM AFTER I INSTALL THE SOFTWARE FOR MY SOUND CARD?
8. CAN I USE THE SAME DMA AND IRQ VALUES FOR BOTH THE PRO AUDIO SPECTRUM 16
AND SOUND BLASTER EMULATION PORTIONS OF THE CARD?
9. I'VE HEARD THAT I MIGHT HAVE AUDIO PROBLEMS IF I HAVE A SYMPHONY CHIPSET ON
MY MOTHERBOARD.  CAN THIS BE CORRECTED?
10. IS THE PRO AUDIO SPECTRUM 16 SUPPORTED UNDER UNIX?
11. WHICH TYPE OF MICROPHONE WILL WORK WITH THE PRO AUDIO SPECTRUM 16?
12. WHAT CAUSES A MEMORY PARITY ERROR?
13. HOW DO I EDIT MY FILES?
14. CAN I LOAD THE MEDIA VISION DEVICE DRIVERS HIGH?
15. WHEN I BOOT MY SYSTEM OR GO INTO WINDOWS, I GET READ ERRORS FROM MY
FLOPPY DRIVE.  WHAT IS HAPPENING?
16. WHY AM I GETTING AN "INCORRECT DOS VERSION" ERROR MESSAGE?
17. HOW DO I CORRECT A "NOT ENOUGH DRIVER LETTERS" ERROR MESSAGE?
18. I'VE INSTALLED THE CARD AND SOFTWARE, BUT I DON'T GET ANY SOUND UNDER DOS
OR WINDOWS.  WHAT IS HAPPENING?
19. AFTER I INSTALLED YOUR CARD, MY MODEM STOPPED WORKING.  IS THIS WHAT IS
CALLED AN IRQ CONFLICT?
20. NONE OF MY GAMES WORK WITH SOUND.  WHAT AM I DOING WRONG?
21. WHY IS MY AUDIO SO NOISY?
22. HOW DO I SAVE MY VOLUME SETTINGS?
23. WHAT DO I NEED TO DO TO GET MY JOYSTICK TO WORK?
24. WHAT ARE THE PINOUTS FOR THE JOYSTICK/MIDI PORT?
25. DOES THE PRO AUDIO SPECTRUM 16 SUPPORT DUAL JOYSTICKS?
26. WHAT IS A MIDIMATE?
27. DO YOU HAVE AN UPGRADE POLICY?
28. WHICH JUMPERS ON THE SOUND CARD SHOULD I CHANGE?
29. WHAT DOES THE "MVSOUND.SYS" STATEMENT DO?
30. HOW DO I CHANGE THE DMA AND IRQ SETTINGS FOR THE PRO AUDIO SPECTRUM 16
SECTION OF THE CARD?
31. WHAT ARE ALL THE SWITCHES FOR "MVSOUND.SYS"?
32. WHAT IS THE LATEST VERSION OF "MVSOUND.SYS"?
33. HOW DO I DISABLE THE SOUND BLASTER COMPATIBILITY MODE?
34. HOW DO I CHANGE THE DMA AND IRQ SETTINGS FOR THE SOUND BLASTER SECTION
OF THE CARD?
35. WHAT DOES THE "SET BLASTER" STATEMENT DO?
36. WHAT IS "TSLCDR.SYS"?
37. WHAT ARE ALL THE SWITCHES FOR "TSLCDR.SYS"?
38. WHAT IS THE CURRENT VERSION OF "TSLCDR.SYS"?
39. WHICH CD-ROM DRIVES WILL WORK WITH MY CARD?
40. CAN I HAVE MORE THAN ONE SCSI HOST ADAPTER IN MY SYSTEM?
41. DO I NEED TO USE THE SCSI HOST ADAPTER ON THE SOUND CARD TO OPERATE 
MY CD-ROM DRIVE?
42. I JUST INSTALLED A SCSI CD-ROM DRIVE THAT IS SUPPOSED TO WORK WITH YOUR
CARD, BUT THE DRIVE ISN'T WORKING.  WHAT DO I DO?
43. WHAT DOES THE MSCDEX.EXE STATEMENT DO?
44. WHY DOES MY SYSTEM HANG WHEN IT TRIES TO LOAD MSCDEX.EXE?
45. I'M GETTING CDR 101 ERRORS. WHAT CAN I DO TO FIX THIS?
46. I'M GETTING A "NO SCSI HOST ADAPTER DETECTED" ERROR MESSAGE.  HOW DO 
I FIXTHIS?
47. MY THIRD PARTY CD-ROM DRIVE IS NOT WORKING.  WHAT GIVES?
48. HOW DO I GET CD AUDIO FROM MY THIRD PARTY CD-ROM DRIVE?
49. HOW DO I INCREASE THE PERFORMANCE OF MY CD-ROM DRIVE?
50. WHAT WILL DECREASE THE PERFORMANCE OF MY CD-ROM DRIVE?
51. WHAT IS WAVETABLE SYNTHESIS?
52. IS MY CARD WAVETABLE UPGRADABLE?
53. WHAT IS THE "KORG WAVETABLE" UPGRADE?  WILL IT WORK ON MY SYSTEM?
54. WHAT ARE THE FEATURES OF THE KORG WAVETABLE UPGRADE CARD?
55. I'M GETTING "ADLIB IS ALREADY IN USE" ERRORS WHEN I TRY 
TO RUN MY DOS APPLICATIONS THROUGH WINDOWS.  HOW DO I 
GET RID OF THIS ERROR MESSAGE?
56. I'M GETTING THE ERROR MESSAGE, "CAN'T FIND VER. 2.00 OF VDMAD.386."
57. WHY IS WINDOWS MAKING THIS ANNOYING LOOPING SOUND WHEN WINDOWS FIRST
STARTS?
58. I'M GETTING AN ERROR MESSAGE TELLING ME TO "LOAD MULTIMEDIA EXTENSIONS"
BEFORE I RUN THE INSTALLATION PROGRAM.  HOW DO GET RID OF THIS MESSAGE?
59. MIDI DOESN'T WORK ON MY SYSTEM.  HOW DO I CONFIGURE THE MIDIMAPPER?
60. EVER SINCE I INSTALLED YOUR CARD, WINDOWS LOCKS UP WHEN I TRY TO EXIT.
WHAT IS HAPPENING?
61. I'M GETTING THE ERROR MESSAGE "CAN NOT SUCCESSFULLY REGISTER THE 
SERVER" WHEN ATTEMPTING TO ACCESS ANY OF THE POCKET TOOLS IN 
WINDOWS. HOW DO I CORRECT THIS PROBLEM?
62. WHY DO ALL OF  MY SOUNDS PLAY FAST?  IT SOUNDS LIKE MY CARD IS ONE 
OF THE CHIPMUNKS.  HOW DO I FIX THIS?
63. MY POCKET CD WON'T WORK.  I'M GETTING THE ERROR MESSAGE,  "THERE IS AN
UNDETECTABLE PROBLEM IN LOADING THE SPECIFIED DEVICE DRIVER."
64. I'M UNABLE TO USE THE MEDIA PLAYER IN WINDOWS TO PLAY AUDIO CDS.  
HOW CAN I CORRECT THIS PROBLEM?
65. I'M ONLY GETTING SOUND FROM ONE CHANNEL WHEN PLAYING A MUSIC CD.
66. IS THERE A SOFTWARE DEVELOPER'S KIT AVAILABLE FOR THE PRO AUDIO 
SPECTRUM 16?
67. HOW DO I GET TBPRO TO WORK?  IT USED TO WORK FINE, BUT IT DOESN'T WORK
ANYMORE.
68. CAN I CONNECT OTHER SCSI DEVICES TO THE PRO AUDIO SPECTRUM?
69. I'M GETTING THE FOLLOWING ERROR MESSAGE WHEN I USE RECFILE.  "FILE 
IS FULL OR BLOCKED." I AM ALSO NOT ABLE TO RECORD 16 BIT FILES.  WHAT 
IS HAPPENING HERE?
70. WHY AM I GETTING A GPF (GENERAL PROTECTION FAULT) IN "USER.EXE" 
WHEN I TRY TO USE POCKET RECORDER?



1. Which are valid DMA channels?

CHANNEL			USAGE
8 BIT CHANNELS:
0			MEMORY REFRESH
1			UNASSIGNED
2			FLOPPY DISK
3			UNASSIGNED

16 BIT CHANNELS, AT ONLY:
4			UNASSIGNED
5			UNASSIGNED
6			UNASSIGNED
7			UNASSIGNED

2. Which are valid IRQ channels?
INT#			Description
IRQ "0"			TIMER *
IRQ "1"			KEYBOARD *
IRQ "2"			RESERVED(XT), CASCADE
IRQ "3"			COM 2 / 4
IRQ "4"			COM 1 / 3
IRQ "5"			HARD DISK(XT), LPT2-AT
IRQ "6"			FLOPPY DISK
IRQ "7"			LPT 1

HIGH ORDER INTERRUPTS
IRQ "8"			REAL-TIME CLOCK
IRQ "9"			CASCADE
IRQ "10"		UNASSIGNED
IRQ "11"		UNASSIGNED
IRQ "12"		UNASSIGNED
IRQ "13"		80287 COPROCESSOR
IRQ "14"		HARD DISK
IRQ "15"		UNASSIGNED

* These interrupts exist on the system board and are not available on the 
bus connector.

3. Which computers will the Pro Audio Spectrum 16 work in?
The Pro Audio Spectrum 16 was designed around the IBM AT specification.  It 
will work in a 486/50 if the bus (I/O CLK) speed is lowered down to 8 
Mhz.  Please note that the bus speed is not the same as the CPU speed.  
The minimum requirements would be a 386 or higher processor.

4. How much disk space is required for loading all the files on the hard drive?
About 5-6 megs for the Pro Audio Spectrum 16.

5. Can I have two sound cards in my computer?
No.  Other than specialized software that would be developed by an end 
user, currently no applications will use more than one 
sound card at a time. Note that the only exception to this rule is if 
you are installing a wavetable upgrade card that was designed to enhance 
your current sound card.

6. My system files are not being updated after I run the installation program.  
How do I fix this?
1) At the DOS prompt, type:

SETVER C:\DOS INSTALL.EXE 6.00   [enter]

DOS will issue a long warning message about compatibility, and you may 
want to read it.

2) Reboot your system.  The change will NOT take effect until the 
system is restarted.

3) Re-install your Media Vision software from floppy disk.  The 
installation  should now work.

4)  Remove INSTALL.EXE from the SETVER list with the following 
command:

SETVER C:\DOS INSTALL.EXE /D   [enter]

Alternately, the computer could be booted from a DOS 5.0 or DOS 6.0 
bootable  diskette.

7. What changes are made to my system after I install the software for my sound card?
Here are the changes to your system files.

CONFIG.SYS

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:7 S:1,220,1,5 M:0 J:1
DEVICE=C:\PROAUDIO\TSLCDR.SYS /D:MVCD001 /W3

(Note:  If your computer uses a Phoenix or Award Bios, add the 
following parameter to the end of the MVSOUND.SYS line:  "/W:0" )

AUTOEXEC.BAT

SET BLASTER=A220 D1 I5 T3
C:\PROAUDIO\MSCDEX.EXE /D:MVCD001 /M:10  /V

SYSTEM.INI

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
CDAudio=mcicda.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=5
irq=11

[opl3.drv]
drumchannel=10

8. Can I use the same DMA and IRQ values for both the Pro Audio Spectrum 16 
and Sound Blaster emulation portions of the card?
No.  You CANNOT use the same DMA and IRQ for the Pro Audio Spectrum 16 
and Sound Blaster emulation portions of the board.  The values MUST be 
different.

9. I've heard that I might have audio problems if I have a Symphony chipset 
on my motherboard.  Can this be corrected?
Yes.  You need to download SYMPFIX.EXE from the Media Vision BBS.  
Follow the directions in the included text file.  If you have a 
Symphony chipset and you are not experiencing any sound problems, then 
you do not need the SYMPFIX patch.  Here is the DEBUG routine used in 
the SYMPFIX patch.  

DEBUG 			[enter]
O A8 05			[enter]
O A9 60 		[enter]
Q 			[enter]

10. Is the Pro Audio Spectrum 16 supported under UNIX?
No.  Unfortunately, there is no support for the Pro Audio 
Spectrum 16 under UNIX.

11. Which type of microphone will work with the Pro Audio Spectrum 16?
The Pro Audio Spectrum 16 accepts dynamic microphones with impedance of 
600 to 20K ohms.

12. What causes a Memory Parity error?
This is typically caused by a DMA conflict.  You will find the DMA 
parameter on the MVSOUND.SYS line in the CONFIG.SYS file.  The 
DMA is set with the D:x parameter.  Many times, increasing the 
DMABUFFERSIZE in the [386Enh] section of the SYSTEM.INI file will 
resolve this problem.  Here is a sample line.

DMABUFFERSIZE=128

13. How do I edit my files?
You can use Notepad in Windows to edit your files, or use the 
EDIT command under DOS.  You can also use the SYSEDIT program in 
Windows.  To use the SYSEDIT program in Windows:
1)  Ensure that you are in the Program Manger window.
2)  Click on FILE under Program Manager.
3)  Click on RUN.
4)  Enter the following on the command line:
SYSEDIT  [enter]
5)  Edit the file.  When you are ready to save the file, click on FILE
then SAVE.
6)  Click on FILE then EXIT to exit the editor.

To use the EDIT program under DOS:

1)  Enter the following at the DOS prompt:
CD\  [enter]
2) Enter the following at the prompt:
EDIT  CONFIG.SYS  [enter]
3)  Edit the file.  When you are ready to save the file, hold down [ALT] + 
[F].  Then, press [X] to exit.  You will be prompted to save the file.  When 
prompted to save the file, press [Y].

14. Can I load the Media Vision device drivers high?
Yes.  The Media Vision device drivers can be loaded into upper memory.  
Here is a sample line to load MVSOUND.SYS into upper memory.

DEVICEHIGH=C:\PROAUDIO\MVSOUND.SYS  D:3  Q:7

Here is sample line to load MSCDEX.EXE into upper memory.

LH  C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

15. When I boot my system or go into Windows, I get read errors from my 
floppy drive.  What is happening?
Check your CONFIG.SYS and AUTOEXEC.BAT files for references to 
your floppy drives.  Unless you typically boot from your floppy drive, none 
of your lines should try to load drivers or TSRs from the a floppy drive.  
Check the PATH statement in your AUTOEXEC.BAT file.  It is likely that 
you will find some reference to your floppy drive on this line.

16. Why am I getting an "Incorrect DOS Version" error message?
This error message is coming from the MSCDEX.EXE line in the 
AUTOEXEC.BAT file.  MSCDEX.EXE is a TSR that is used in 
conjunction with a  CD-ROM drive.  

NOTE:  If you don't have a CD-ROM drive, you can delete this line from 
your AUTOEXEC.BAT file.  You can also delete the CD-ROM driver line 
in your CONFIG.SYS file.  

MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a DOS 
version sensitive program. If you do have a CD-ROM drive, use these 
steps to resolve the problem.

1)  Use the MSCDEX.EXE from the DOS directory.   Here is a sample 
line.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

2)  Assign the drive letter to the CD-ROM drive (on the MSCDEX line in 
the AUTOEXEC.BAT) with the /L:$  parameter.  Here is a sample line:

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:D

where $ is the drive letter for the CD-ROM drive.  In our example, 
the CD-ROM drive is assigned as drive D.

3)  Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=E

where $ is at least one drive letter BEYOND the last physical drive on the 
system.  Again, in our example  the CD-ROM drive letter is D.

17. How do I correct a "not enough driver letters" error message?
You need to make the following changes to correct this error.

1)  Assign the drive letter to the CD-ROM drive (on the MSCDEX line in 
the AUTOEXEC.BAT) with the /L:$  parameter.  Here is a sample line:

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:D

where $ is the drive letter for the CD-ROM drive.  In our example, 
the CD-ROM drive is going to be drive D.

2)  Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=E

where $ is at least one drive letter BEYOND the last physical drive on the 
system.  Again, in our example  the CD-ROM drive letter is D.

18. I've installed the card and software, but I don't get any sound under 
DOS or Windows.  What is happening?
The first thing to do is to make sure the sound card is functioning 
properly under DOS.

Here is a sample configuration for your CONFIG.SYS file:

DEVICE=C:\PROAUDIO\MVSOUND.SYS  D:5  Q:10 S:1,220,1,5 M:0 J:1 T:1 /W:0

Test the DMA and IRQ settings using PLAYFILE under DOS.

Reboot the system.  Make sure your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PROAUDIO).  Note that 
you may use something other than the TEST.WAV file to test your 
sound. ).  Test the sound by entering the following line:

PAS  RESET			[enter]
PLAYFILE  TEST.WAV		[enter]

You should hear the sound of a phone dialing.  If you hear no sound, 
enter the following at the DOS prompt:

DEBUG 				[enter]
O A8 05				[enter]
O A9 60 			[enter]
Q 				[enter]

Try the PLAYFILE command again.  If this now works, download 
SYMPFIX.EXE from the Media Vision BBS, and follow the directions in 
the included text file.

If this doesn't work, try a different DMA / IRQ combination. 

You should also try the card in a different slot.  Make sure the BUS 
speed on your system is set to 8.33 Mhz.

Once you  have sound in DOS, Windows should also have sound.  
If you have no sound  in Windows, make sure the DMA and IRQ 
settings match the D: and Q: parameters on the MVSOUND line.
The DMA and IRQ settings for Windows can be found in the 
[mvproaud.drv] section near the bottom of the SYSTEM.INI file.

19. After I installed your card, my modem stopped working.  Is this what is 
called an IRQ conflict?
Yes, this is an IRQ conflict.  It is likely that you are using IRQ 3 for your 
sound card as well as your modem.  You will need to stop using IRQ 3 for 
the sound card.  Here are some steps to assist you in finding a suitable 
IRQ.

Make the following changes to your system files:

CONFIG.SYS

DEVICEHIGH=C:\PROAUDIO\MVSOUND.SYS D:3 Q:10 S:1,220,1,7 M:0 J:1

Make sure this is the last line in your CONFIG.SYS file.

AUTOEXEC.BAT

SET  BLASTER=A220  D1  I7  T3

Test the DMA and IRQ settings using PLAYFILE under DOS.

Reboot the system.  Make sure your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PROAUDIO).  Note that 
you may use something other than the TEST.WAV file to test your 
sound. ).  Test the sound by entering the following line:

C:\PROAUDIO>PLAYFILE  TEST.WAV	 [enter]

You should hear the .WAV file play once.

If this does not sound normal, adjust the IRQ setting on the 
MVSOUND.SYS line in your CONFIG.SYS file.

Once you  have sound in DOS, Windows should also have sound.  
If you have no sound  in Windows, make sure the DMA and IRQ 
settings match the D: and Q: parameters on the MVSOUND line.
The DMA and IRQ settings for Windows can be found in the 
[mvproaud.drv] section near the bottom of the SYSTEM.INI file.

20. None of my games work with sound.  What am I doing wrong?
The lack of sound is probably related to insufficient conventional memory 
for the program.

Consult your DOS manual regarding memory management.  The Media 
Vision drivers can load into upper memory without any problems. We 
recommend that your conventional memory be at least 590 kb, which 
should be adequate to run most applications.

If enough memory cannot be made available, you may need to create a 
boot disk, with a minimal number of drivers.

Finally, refer to your instruction manual that came with the game.  
If all else fails, you may need to contact the game manufacturer.

21. Why is my audio so noisy?
When used in computers having certain combinations of hardware 
(processor, BIOS, and chipset), the Pro Audio Spectrum sound cards can 
produce static, popping, and hiss.  The following presents several solutions 
available to you.

First, try adding a T:1 as well as a /W:0 to the end of the MVSOUND line 
in the CONFIG.SYS.  For example:

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:3 Q:7 S:1,220,1,5 M:0 J:1 T:1 /W:0

Restart your computer, and see if the noise goes away.  If not, try adjusting 
your DMA settings.  You may want to switch to  16 bit DMA IRQ settings 
if you are currently using 8 bit DMA and IRQ settings.  If you are currently 
using  16 bit DMA and IRQ settings,  try dropping down to 8 bit DMA and 
IRQ settings.  We recommend that you use the same DMA and IRQ 
setting for both DOS and Windows.  The DMA setting for Windows can 
be found near the bottom of the SYSTEM.INI file in the 
[mvproaud.drv] section.  Usually the DMA change and the 
addition of the T:1 eliminates the popping and static noise.  

You may also want to investigate your mixer settings.  Make sure you 
do not have something turned up too much.  Check the mixer 
settings by using the PAS utility under DOS.  

To view the settings, type:

PAS  *		[enter]

If  you would like to reset the DOS mixer, you can type the following 
at a DOS prompt:

PAS RESET	[enter]


Under Windows use the Pocket Mixer to check your settings.

22. How do I save my volume settings?
Volume settings for the Pro Audio Spectrum 16 can be set to
a predetermined set of values when the computer starts up.  Here's how:

1) At the DOS prompt, type:

PAS *  	[enter]

2) Adjust the volume settings to the desired levels.

3) Hold down <SHIFT> and press the function key F5.  This saves the 
mixer settings under the F5 setting.  To test the procedure, press the F4 
key.  This will reset the mixer to the default volume levels.  Press the F5 
key, and your saved volume settings should be recalled.

4) Press the <ESC> key to exit the mixer.

5) Edit your AUTOEXEC.BAT file.

6) Check to see if the Media Vision directory is in the PATH statement.  
Add it if it isn't.

7) Add a new line underneath your PATH statement:

PAS F5  (Note: you may also use: PAS SET F5)

8) Save the changes to the AUTOEXEC.BAT.  Reboot.  Your new volume 
levels should be automatically set every time you start the computer.

23. What do I need to do to get my joystick to work?
You need to turn "on" the Joystick port on the MVSOUND.SYS line,  
using the "J:x" parameter.  Here is a sample line that has the game port 
turned "on."

DEVICE=C:\PROAUDIO\MVSOUND.SYS  D:3  Q:7  S:1,220,1,5  M:0 J:1

The following are some other tips to ensure your joystick port works.

1)  Make sure that you have only one active game port on your system.  
Some motherboards have a built-in game port.  You will need to disable the 
built in game port to use the game port on the sound card.  It doesn't 
matter which game port you use.   So, if you are unable to disable a game 
port already on the system, just disable the game port on the sound card.

"J:1" turns the joystick on.
"J:0" turns the joystick off.

2)  Try turning off the TURBO switch on your PC.  

3)  Try putting the card in a different slot.

4)  Make sure that the BUS speed on your system is set to 8 Mhz.

Some hard drive controllers and motherboards may have a joystick port 
built into them.  Remove the sound card and connect the joystick to the 
Multi I/O card game port.  If it works, the game port is NOT disabled.

Sometimes you will not be able to find the actual port that you would plug 
the joystick into, however, the interface may still be there and enabled!  
Look on all cards (including the motherboard) for 16-pin header 
connectors with nothing plugged into them.  It is possible that this is a 
header connector for a joystick interface. 

Finally, you may need to reinstall your game to get the joystick recognized 
by the software.

24. What are the pinouts for the Joystick/Midi port?

1	+5VDC
2	JOYSTICK 1 FIRE 1
3	JOYSTICK 1 X
4	GROUND
5	GROUND
6	JOYSTICK 1 Y
7	JOYSTICK 1 FIRE 2
8	+5VDC
9	+5VDC
10	JOYSTICK 2 FIRE 1
11	JOYSTICK 2 X
12	MIDI OUT  (GROUND on MIDI Mate)
13 	JOYSTICK 2 Y
14	JOYSTICK 2 FIRE 2
15	MIDI IN (+5VDC on MIDI Mate)

25. Does the Pro Audio Spectrum 16 support dual joysticks?
No.  The Pro Audio Spectrum 16 will NOT support dual joysticks in its current 
configuration.  Here are the pinouts to create a modified joystick to 
support a dual joystick.

D15S (male)------------D15S(female)
to PAS-----------------to joystick
1--------------------------1
2--------------------------2
3--------------------------3
4--------------------------4
5--------------------x-----5
6---------------------|----6
7---------------------|----7
8---------------------|----8
9 -----x--------------|----9
10----|...............|---10
11----|...............|---11
12----|...................12
13----|-------------------13
14----|-------------------14
15....|-------------------15

(........) = no connection

If you have a Midimate, the Midimate joystick port will support dual 
joysticks.

26. What is a Midimate?
A Midimate is a device that will allow you to connect a music keyboard to 
your sound card.  The Midimate connects to the joystick/midi connector 
and your music keyboard.

27. Do you have an upgrade policy?
Media Vision does not currently have an upgrade program.

28. Which jumpers on the sound card should I change?
None.

29. What does the "MVSOUND.SYS" statement do?
It initializes and enables the Pro Audio Spectrum 16 to produce sound under 
DOS.

30. How do I change the DMA and IRQ settings for the Pro Audio Spectrum 16 
section of the card?
The DMA and IRQ settings for the sound card are software controllable.  
You will need to modify the D:# and Q:# parameters on the 
MVSOUND.SYS line in your CONFIG.SYS file. 

See "What are all the switches for 'MVSOUND.SYS'?" for even 
more information regarding the D:# and Q:#  parameters.  

Here is a sample MVSOUND.SYS line.  In this example, the DMA will be 
3 and the IRQ will be 7.

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:3  Q:7  S:1,220,1,5 M:0 J:1

31. What are all the switches for "MVSOUND.SYS"?
Options:
D:#	# = PAS DMA Channel		(default: 3)
Q:#	# = PAS IRQ Channel		(default: 7)
S:#	# = SB on/off,port,dma,irq	(default: 1,220,1,5)
M:#	# = MPU on/off,port,irq		(default: 0,330,2)
J:#	# = Joystick status, 1=on-0=off (default: 1)
V:#	# = Volume Level, 0-100 (%)	(default: 80)
T:#	# = Clock Source, 0(CPU)/1(PAS) (default: 0)
/W:#	Allow Warm Boot, 1(on) or 0(off)(default: 1)
G	Increase Gain			(default: off)
X	display PAS configuration found
U	Unload driver after configuration

32. What is the latest version of "MVSOUND.SYS"?
As of September 1994, the latest version of MVSOUND.SYS is 3.24.  The 
file is available on the BBS or Compuserve as MVSND324.EXE

33. How do I disable the Sound Blaster compatibility mode?
You will need to modify the MVSOUND.SYS line in your CONFIG.SYS 
file.  Use the S:# parameter to enable or disable the Sound Blaster emulation.
Here is a sample line with Sound Blaster emulation disabled

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:3 Q:7 S:0 M:0 J:1

See "What are all the switches for MVSOUND.SYS?" for even more 
information regarding the S:# parameter.

34. How do I change the DMA and IRQ settings for the Sound Blaster section 
of the card?
You will need to modify the MVSOUND.SYS line in your CONFIG.SYS 
file. Use the S: parameter to configure the Sound Blaster emulation.  Here 
is a sample line with Sound Blaster emulation enabled using DMA 1, IRQ 
5, and I/O ADDRESS 220.  Remember, you must also modify the SET 
BLASTER statement in the AUTOEXEC.BAT file as well.

CONFIG.SYS

DEVICE=C:\PROAUDIO\MVSOUND.SYS  D:3  D:7  S:1,220,1,5  M:0 J:1

(Note: S:# = SB on/off,port,dma,irq)

AUTOEXEC.BAT

SET BLASTER=A220  D1  I5  T3

(Note: A=PORT  D=DMA  I=IRQ  T=Sound Blaster emulation mode)

35. What does the "SET BLASTER" statement do?
The SET BLASTER statement sets environment variables for the Sound 
Blaster emulation on your card that many multimedia applications need to 
function properly.

36. What is "TSLCDR.SYS"?
TSLCDR.SYS is the device driver for SCSI CD-ROM drives that use the 
Pro Audio Spectrum 16 as a SCSI host adapter.  It was written by Trantor for 
Media Vision.  Media Vision fully supports this driver.

37. What are all the switches for "TSLCDR.SYS"?
Syntax:

DEVICE=C:\PROAUDIO\TSLCDR.SYS /D:MVCD001 /R /P3 /W0

where /D:MVCD001  is the logical device name.  This needs to match logical 
device name used on the MSCDEX.EXE line in the AUTOEXEC.BAT file.

/R	Reset SCSI bus on CPU reset

/P#	0 Disables seek and prefetch modes
	1 Enables seek mode
	2 Enables prefetch mode
	3 Enables both seek and prefetch modes
	(Note there is no colon here!)

/W#	0 Do not pause
	2 Pause if SCSI device detected
	3 Pause if no SCSI device detected

38. What is the current version of "TSLCDR.SYS"?
As of December 1994, the current version of TSLCDR.SYS is 3.18.

39. Which CD-ROM drives will work with my card?

Note: numbers surrounded by brackets indicate a footnote.

CD-ROM DRIVES SUPPORT LIST
REV. December, 1994

INTERNAL SCSI CD-ROM DRIVES
Chinon			CDS-431[#6], CDS-435[#4], CDS-535[#1]
Hitachi			CDR-3650 (with rev. 0008 ROM or later), 
			CDR-3750[#3]
NEC			CDR-55JD[#2], CDR-80[#5], CDR-82, CDR-
			83[#3], 
			CDR-83J[#3],CDR-83M[#3], CDR-84[#3], 
			CDR-84J[#3],
			CDR-84-1[#2], CDR-500[#2] 
Philips			CM-425A[#1] 
Sanyo			CDR H93MV, CDR H94S
Sony			CDU-541[#3], CDU-561[#2], CDU-561-31[#1]
			CDU-55S 
Teac			CD-50[#1] (Firmware Rev. 1.00 only)
Texel			DM-3020, DM-302[#1], DM-3024[#2], DM-
			3028[#1] 
Toshiba			XM-3201B[#3], XM-3401B[#2]

EXTERNAL SCSI CD-ROM DRIVES
Apple			CD-SC (Sony CDU-8001), CD-SC Plus (Sony 
			CDU-8002), 
			CD-300 (Sony CDU-8003)[#1]
CD Technologies	Porta-Drive
Chinon			CDC-431[#6], CDX-431[#6], CDC-435[#3], CDX-
			435[#3], CDX-535[#1] 
Denon			DRD-253
Hitachi			CDR-1553S, CDR-1650, CDR-1750S[#3] 
IBM			3510
Laser Magnetics		CM-212, CM-214, CM-231[#3]
Media Vision		ReNO[#1]
NEC			CDR-25[#3], CDR-25BJ[#3], CDR-35[#5], 
			CDR-36, 
			CDR-36M[#3], CDR-37[#3], CDR-38[#2], 
			CDR-72, 
			CDR-73[#3],CDR-73M[#3], CDR-74[#3], 
			CDR-74-1[#2], 
			CDR-77[#5], CDR-400[#2], CDR-600[#2] 
Panasonic		CR-501-S[#6] (Firmware Rev. 1.0b or later)
Pioneer			DRM-600[#3] (6 disk changer)
Sony			CDU- 6110[#3], CDU-6111[#3], CDU-6211[#3], 
			CDU-7211[#3]
Sun			Sony CDU-8012[#1]  (Photo CD Single Session 
ONLY)
Texel			DM- 3010, DM-3120, DM-5010, DM-5020, DM-
			502[#1], DM-5022, DM-5024[#2], DM-5028[#1],
			DM-5110, DM-5120, DM-7120A, DM-7120B
Toshiba			XM-3100, XM-3101, XM-3201A[#3], XM-	3301[#3], 
			XM-3301TA[#2], XM-3401P or E[#2], XM-5100A
Notes:
[#1]    Requires TSLCDR.SYS ver. 3.18.
[#2]    Will support Photo CD Multi Session when using the 
TSLCDR.SYS ver. 3.02 or later.
[#3]    Will support Photo CD Single Session when using the 
TSLCDR.SYS driver ver. 1.46F or later.
[#4]    Requires TSLCDR.SYS ver. 3.02, and supports Photo CD 
Single Session.
[#5]    TSLCDR.SYS ver. 1.46 or later will not support these CD-ROM 
drives because of the hardware differences with Photo CD compatibility, 
however, version 1.44 will support them.  Please contact Customer 
Service and request TSLCDR.SYS ver. 1.44 (Requires PAS16 or 
older sound card).  
[#6]    Doesn't support photo CD.

Not all CD-ROMs support CD audio (redbook).  Some CD-ROMs are 
data only; check with the manufacturer of the drive.  Chinon CDS-431 may 
require a 40 to 50 pin converter; contact Chinon at (310)533-0274 to 
obtain it. If the CD ROM drive is not on the list and it supports the SCSI 2 
command set, then driver version 3.18 may support it.  Sony drives older
than the CDU-541 are not supported by TSLCDR.SYS version 3.18.

ADDITIONAL INFORMATION:
Cables for most of the SCSI CD-ROM drives listed above are available 
from any dealer that sells Multimedia supplies.  For a referral, contact 
Customer Service.  To obtain SCSI or ASP drivers for other types of 
SCSI devices (optical drives, hard disks, removable drives, etc.), contact 
Adaptec at 1-408-945-8600 and ask for "pre-sales", and get the product 
called SCSIworks! by Trantor.

40. Can I have more than one SCSI host adapter in my system?
Yes.  You can have as many SCSI host adapters in the same system 
as there are available slots.  The Pro Audio Spectrum 16's SCSI will 
not interfere with other SCSI adapters.  The only possible conflicts would 
be with DMAs, IRQs, or I/O ports used by another card.

41. Do I need to use the SCSI host adapter on the sound card to operate my 
CD-ROM drive?
No.  The only connection you need to make is a CD-Audio 
connection.  You would only need to make this connection if you plan on 
using the mixer on the sound card to control CD-Audio.  You can purchase 
an Audio cable for your CD-ROM drive and sound card from 
Advanced Multimedia Concepts "AMC".  AMC can be reached at 
(800)-882-0587.

42. I just installed a SCSI CD-ROM drive that is supposed to work with 
your card, but the drive isn't working.  What do I do?

Make sure you are using the proper version of TSLCDR.SYS for your 
CD-ROM drive.

Make sure you have a LASTDRIVE statement in your CONFIG.SYS file:

LASTDRIVE=$

where $ is at least one drive letter BEYOND the last physical drive on the 
system.

Try the following sample lines in place of your current lines in the 
CONFIG.SYS file:

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PROAUDIO\TSLCDR.SYS /D:MVCD001 /R

Make sure these are the last two lines in your CONFIG.SYS file.

Also make sure you are using the latest version of  MSCDEX.EXE 
on your system. Make sure the MSCDEX.EXE line in the 
AUTOEXEC.BAT file is at the top of the file.   Also, assign the 
drive letter to the CD-ROM drive with the /L:$ parameter. Here is a 
sample line for your AUTOEXEC.BAT file that will ensure 
you are using the proper version of MSCDEX.EXE for your system:

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

where $ is the drive letter assigned to the CD-ROM drive.  

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

43. What does the MSCDEX.EXE statement do?
MSCDEX.EXE is a TSR used in conjunction with a  CD-ROM 
driver.  MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a 
DOS version sensitive program.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure you are using the proper 
version of MSCDEX.EXE for your system:

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

44. Why does my system hang when it tries to load MSCDEX.EXE?
Make sure that you are loading MVSOUND.SYS before TSLCDR.SYS.    
Also make sure that the "name" of the CD-ROM drive matches on the 
TSLCDR.SYS and MSCDEX.EXE lines.  The "name" of the drive should 
be:

MVCD001

Run MSD to find out what TSLCDR.SYS is using for a "name" for the 
CD-ROM drive.  Sometimes TSLCDR.SYS will ignore the "name" that is 
specified on the TSLCDR.SYS line in the CONFIG.SYS file.  MSD will 
tell us what it is really using.

When in MSD, look at the DEVICE DRIVERS section.  In the DEVICE 
DRIVERS section you will see several headings at the top of the screen.  
The first heading will be DEVICE, and the second heading will be 
FILENAME. 

Find TSLCDR under the FILENAME heading.   You will then see the 
"name" over to the right of TSLCDR (under the DEVICE column) that 
TSLCDR.SYS is using for the CD-ROM.  If the "name" is something other 
than "MVCD001," use whatever TSLCDR.SYS wants to use.  

Remember to use this "name" on the TSLCDR.SYS line and the 
MSCDEX.EXE line.

You might also try the following sample lines in place of your current lines 
in the CONFIG.SYS file:

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PROAUDIO\TSLCDR.SYS /D:MVCD001 /R

Make sure the MSCDEX.EXE line in the AUTOEXEC.BAT file is at 
the TOP of the file.  Here is a sample line:

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

45. I'm getting CDR 101 errors. What can I do to fix this?
Troubleshoot  your CD-ROM drive while in DOS. A CDR 101 error is a 
very difficult error to troubleshoot via FAQ.  Here are all possible 
troubleshooting tips to either eliminate the problem, or at least 
narrow it down.  The PC is assuming that the driver is loaded properly, but 
the CD-ROM drive is having problems reading the disk. Try the 
following.

1) Make sure you are not trying to read an audio disc.

2)  Check the internal flat ribbon cable.  Disconnect and reconnect the 
ribbon cable that connect the CD-ROM drive to the sound card.  Do this at 
both ends of the cable.  Try a different or new ribbon cable; the cable could 
be bad.  

If the cable is connected correctly to the card, it is 
possible that the cable is plugged in backwards on the CD-ROM drive.  
In most cases the drive's connector is "keyed" so the cable cannot be 
put on wrong, however, it is possible to force the cable on incorrectly.  
Check the cable for damage, kinks, or stretching to the maximum length.  
Make sure the ribbon cable is installed with the colored edge up 
(toward the 4 pin connector, J4) and is seated completely.  When you 
re-install the cable, check for bent pins; also, check the cable to make 
sure it is not off-set where it is not covering all of the pins.

3)  Make sure there is a LASTDRIVE statement in the CONFIG.SYS and 
that it is high enough to cover the CD-ROM drive plus one drive.  In other 
words, if the CD-ROM drive is drive E, then the statement should read as 
follows:

LASTDRIVE=F

This is a requirement of MSCDEX.EXE.  You don't need a LASTDRIVE 
statement if the CD-ROM drive is drive D.

4)  The CD-ROM driver ideally should be located at the bottom of the 
CONFIG.SYS file.  Very rarely should it be at the top of the file.  If the 
CD-ROM driver loads first, it's possible to cause other problems.  

As a test, move MVSOUND.SYS  and the CD-ROM driver to the top 
of the CONFIG.SYS file.  Make sure that you are using the latest 
version of  MSCDEX.EXE on your system.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure you are using the proper 
version of MSCDEX.EXE for you system:

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10  /L:$

where $ is the drive letter for the CD-ROM drive.  This is where you will 
assign the drive letter to the CD-ROM drive.

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

If you ran Memmaker and it put memory locations at the front of 
the Media Vision lines, remove the memory locations.  Here is a 
sample line that loads the a driver high without the memory location:

DEVICEHIGH=C:\PROAUDIO\MVSOUND.SYS  D:5  Q:10

5)  If your drive uses a caddy, make sure the caddy lid is closed.  Make 
sure the metal door on the caddy will move smoothly to the left or right 
and return freely to the center.  Try a different caddy.  Make sure the 
CD is not skewed in the drive bay or the CD caddy.  

Confirm that the CD is not up-side down.  In the drive bay, you can read 
the label of the CD when the drive door is open.  With a caddy, you can 
see the label of the CD through the clear plastic.

Remove the CD from the CD-ROM drive; replace it with a different CD, 
or use a replacement of the original CD.  See if the same error occurs.  If
you have no more errors, the first CD was bad.  If it continues with 
the same problem, something else is wrong.

6)  Re-seat the card.  Carefully pull the card out of the slot it 
currently is in and replace it in the same slot.  Or, pull the card 
out of its current slot, and put it into a different slot.

7)  Reduce your CONFIG.SYS and AUTOEXEC.BAT  files to the bare 
minimums.  You will only want to load MVSOUND.SYS and 
TSLCDR.SYS in the CONFIG.SYS.  In the AUTOEXEC.BAT file, you 
will only want to load MSCDEX.EXE.

If these suggestions don't work, the drive needs to be serviced.

46. I'm getting a "No SCSI host adapter detected" error message.  How 
do I fix this?
1)  Make sure that the SCSI host adapter is being found when your system 
boots.  Reseat ALL cables and the Sound card.  Try booting the system 
with no SCSI cable attached. You should receive a message from the 
TSLCDR.SYS line that tells you that a SCSI host adapter was detected at 
address 388h.   If you still receive a "No SCSI host adapter detected," then 
try moving the card to another slot. 

If the SCSI host adapter is detected when the SCSI cable is not connected, but 
not when it is connected, then you have a bad SCSI cable. Replace the 
cable, and everything should work correctly.  Once the host adapter is 
detected, if you are still having problems, try the tips below.  

2) Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=$

where $ is at least one drive letter BEYOND the last physical drive on the 
system.

3)  Try the following sample lines in place of your current lines in the 
CONFIG.SYS file:

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PROAUDIO\TSLCDR.SYS /D:MVCD001 /R

Make sure these are the last two lines in your CONFIG.SYS file.  
Make sure TSLCDR.SYS is the very last line in the file.

4)  Make sure you are using the latest version of  MSCDEX.EXE on 
your system.  Make sure the MSCDEX.EXE line in the AUTOEXEC.BAT 
file is at the TOP of the file.  Also, assign the drive letter to the CD-ROM 
drive with the /L:$ parameter. Here is a sample line for your 
AUTOEXEC.BAT file that will ensure you are using the proper 
version of MSCDEX.EXE for you system:

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

where $ is the drive letter for the CD-ROM drive.  

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

47. My third party CD-ROM drive is not working.  What gives?

Make sure you have a LASTDRIVE statement in your CONFIG.SYS file:

LASTDRIVE=$

where $ is at least one drive letter BEYOND the last physical drive on the 
system.

Try the following sample lines in place of your current lines in the 
CONFIG.SYS file.

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PROAUDIO\TSLCDR.SYS  /D:MVCD001  /R

Make sure these are the last two lines in your CONFIG.SYS file.

Make sure you are using the latest version of  MSCDEX.EXE on 
your system.  Make sure the MSCDEX.EXE line in the AUTOEXEC.BAT 
file is at the TOP of the file.  Also, assign the drive letter to the CD-ROM 
drive with the /L:$ parameter. Here is a sample line for your 
AUTOEXEC.BAT file that will ensure you are using the proper 
version of MSCDEX.EXE for you system:

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

where $ is the drive letter for the CD-ROM drive.  

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

48. How do I get CD audio from my third party CD-ROM drive?
You can purchase an Audio cable for your CD-ROM drive and sound 
card from Advanced Multimedia Concepts "AMC".  AMC can be 
reached at (800)-882-0587.

49. How do I increase the performance of my CD-ROM drive?
1) Increase M-parameter (memory buffers) on MSCDEX.EXE (32 is 
max.)
2) Use /W:0 switch on MVSOUND in CONFIG.SYS.
3) Use expanded memory , and the /E switch on MSCDEX (only on 
certain computers.)
4) Use /R switch on TSLCDR.SYS (or remove if present.)
5) Use /P3 parameter on TSLCDR.SYS (or remove if present.)
Note that using this parameter with NEC CD-ROM drives is not 
advised.
6) Try using the CD-ROM caching feature in SMARTDRV that 
comes with DOS 6.2.  To ensure that SMARTDRV is caching
your CD-ROM drive, make sure you do not have the /U switch on
your SMARTDRV line. 

50. What will decrease the performance of my CD-ROM drive?
Here are some things that reduce CD-ROM performance:

1) Loading MSCDEX into high memory (most common).
2) Incorrect MSCDEX for your DOS version (common).
3) Using expanded memory , and the /E switch on MSCDEX (only on 
certain computers).
4) Sound card conflicts (DMA, IRQ, or port address).
5) Loading CD-ROM driver into high memory (uncommon).
6) Have colon on P-parameter on TSLCDR.SYS (i.e., change /P:3  to /P3).
7) Using an incorrect version of TSLCDR.SYS.
8) Using the CD-ROM caching that defaults with SMARTDRV that 
comes with MS-DOS 6.2.  To disable the caching feature, add the 
/U switch on your SMARTDRV line.

51. What is wavetable synthesis?
Wavetable synthesis uses a digital recording samples of real 
instruments to play MIDI music.

52. Is my card wavetable upgradable?
The Pro Audio Spectrum 16 is not a wavetable upgradable sound card.  The 
Premium and Pro 3-D sound cards from Media Vision are wavetable 
upgradable.

53. What is the "Korg Wavetable" upgrade?  Will it work on my system?
The Korg Wavetable upgrade card is a Waveblaster-compatible upgrade card.  
As long as your card is Waveblaster-compatible, the Korg card will work on 
your system.  The Korg Wavetable upgrade card does not work with the PAS 16.

54. What are the features of the KORG wavetable upgrade card?
The features include:

General MIDI compatible
WaveBlaster compatible feature connector
32 voice polyphony (simultaneous notes)
16 part multitimbral (16 instruments at once)
4Mb of sample ROM containing: 
	128 musical instruments
	4 drum set/effects of 47 instruments each
32 oscillators
32 dynamic digital low-pass filters
Onboard DSP provides Reverb and Chorus effects.

55. I'm getting "ADLIB is already in use" errors when I try to run my DOS 
applications through Windows.  How do I get rid of this error message?
This type of error means you are loading unnecessary drivers 
when you load Windows.  Check your SYSTEM.INI file for any of the 
following drivers.  If you find any of these, remark them out of the 
file with semicolons (;;).  These lines are in the [386Enh] section of 
your SYSTEM.INI file.

DEVICE=VADLIBD.386
DEVICE=VSBD.386
DEVICE=VSBPD.386
DEVICE=VSGLX16.386
DEVICE=VSGLD.386
DEVICE=VSGD.386
DEVICE=VSGLX.386

56. I'm getting the error message, "Can't find ver. 2.00 of VDMAD.386."
Some Windows applications replace this driver by their own DMA driver.  
To correct this problem, edit your SYSTEM.INI file.  Look in 
the [386Enh] section for the following line:

DEVICE=VDMADX.386

Comment this line out of your file with semicolons (;;).

;; DEVICE=VDMADX.386

Then, add the following statement to the very beginning of the [386Enh] 
section:

DEVICE=*VDMAD

Restart Windows.  The error message should disappear.

57. Why is Windows making this annoying looping sound when Windows 
first starts?
You are having an IRQ conflict.  You should be able to resolve this
easily by making following changes to your system files.

CONFIG.SYS

DEVICEHIGH=C:\PROAUDIO\MVSOUND.SYS  D:3  Q:12  S:1,220,1,7 M:0  J:1

Test the DMA and IRQ settings using PLAYFILE under DOS.

Reboot the system.  Make sure your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PROAUDIO).  Note that 
you may use something other than the TEST.WAV file to test your 
sound. ).  Test the sound by entering the following line:

C:\PROAUDIO>PLAYFILE  TEST.WAV	 [enter]

You should hear the .WAV file play once.

If this does not sound normal, adjust the IRQ setting on the 
MVSOUND.SYS line in your CONFIG.SYS file.

Once you  have sound in DOS, Windows should also have sound.  
If you have no sound  in Windows, make sure the DMA and IRQ 
settings match the D: and Q: parameters on the MVSOUND line.
The DMA and IRQ settings for Windows can be found in the 
[mvproaud.drv] section near the bottom of the SYSTEM.INI file.

58. I'm getting an error message telling me to "load Multimedia Extensions" 
before I run the installation program.  How do get rid of this message?
Before you can successfully install the Window drivers, you need to edit 
your SYSTEM.INI (in the Windows directory).  Look in the [boot] 
section, and locate a line that looks like this:

DRIVERS=MMSYSTEM.DLL

If this line is gone, add it.  If  anything else is on the end of this 
line, put two semicolons in front of the whole line.  Here is an example:

;; DRIVERS=MMSYSTEM.DLL POWER.DRV

Add a new line directly below the original.  Type it just like the first 
sample line above.  Save the file; re-boot Windows.  Now you can run the 
installation.  After it has completed, remove the new line, and remove the 
semicolon on the original.

59. MIDI doesn't work on my system.  How do I configure the Midimapper?
1) Double-click on Control Panel (in the Main group).
2) Double-click on MIDIMAPPER.
3) Click on NEW.  A dialog box will come up.
4) Enter "Music1" in the name field.
5) Click on OK.  A grid will now come up.
6) In the center column, titled "PORT NAME," click once on [None] to  
bring down a list of available MIDI sound sources.
7) Select "MVI OPL3 FM Synthesizer."  This selection uses the sound 
card to create the MIDI sound for MIDI channel 1.
8) Repeat steps 6 and 7 for MIDI channels 1-10, and 13-16.
9) In the second column, titled "DEST Channel," click once on channel 
16.  
10) Using the up and down arrows, change this to 10.  This maps Source 
Channel 16 to Destination Channel 10 (for percussion).
11) Click on OK.  When prompted to save the changes, click on YES.
12) Click on the CLOSE button located near the right of the screen.

60. Ever since I installed your card, Windows locks up when I try to exit.  
What is happening?
When exiting Windows, a .WAV file is trying to play.  The sound card is 
not able to play the .WAV file, and at this point, the computer is waiting 
for the file to be played.  It is likely that you are having an IRQ or DMA 
conflict.  

Here is a sample line for your CONFIG.SYS file:

CONFIG.SYS

DEVICE=C:\PROAUDIO\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 T:1 /W:0

You should first determine that you do not have an IRQ conflict by 
testing the IRQ values under DOS.  Here is a simple test that will tell 
you whether or not you have a solid IRQ setting.

Test the DMA and IRQ settings using PLAYFILE under DOS.

Reboot the system.  Make sure your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PROAUDIO).  Note that 
you may use something other than the TEST.WAV file to test your 
sound. ).  Test the sound by entering the following line:

PAS  RESET		[enter]
PLAYFILE  TEST.WAV	[enter]

You should hear the sound of a phone dialing.  If you hear no sound,
enter the following at the DOS prompt:

DEBUG			[enter]
O A8 05			[enter]
O A9 60			[enter]
Q			[enter]

Try the PLAYFILE command again.  If this now works, download 
SYMPFIX.EXE from the Media Vision BBS, and follow the directions in 
the included text file.

If this does not work, try a different DMA / IRQ combination.

Once you  have sound in DOS, Windows should also have sound.  
If you have no sound  in Windows, make sure the DMA and IRQ 
settings match the D: and Q: parameters on the MVSOUND line.
The DMA and IRQ settings for Windows can be found in the 
[mvproaud.drv] section near the bottom of the SYSTEM.INI file.

Here are the changes that should have been made to your SYSTEM.INI.

SYSTEM.INI

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
CDAudio=mcicda.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=x	    (this is the D: value on the MVSOUND.SYS line in the 
CONFIG.SYS)
irq=y	    (this is the Q: value on the MVSOUND.SYS line in the 
CONFIG.SYS)

[opl3.drv]
drumchannel=10


If changing the values for the DMA and IRQ settings doesn't help,
download the GWPATCH.EXE file from the BBS.

GWPATCH.EXE is a file that contains a different mix of Windows drivers 
that will often solve Windows lock ups.

GWPATCH.EXE contains the following files:

File: MVMIXER.DRV
Size: 41200
Date: 09-21-93
Time: 2:14p

File: MVPROAUD.DRV
Size: 27344
Date: 08-26-93
Time: 2:31p

File:VPASD.386
Size: 15967
Date: 08-26-93
Time: 2:31p

File: MMMIXER.DLL
Size: 22800
Date: 09-07-93
Time: 9:41a

61. I'm getting the error message "can not successfully register the 
server" when attempting to access any of the Pocket Tools in Windows. 
How do I correct this problem?
The problem can be traced to a corrupted REG.DAT file in the 
WINDOWS directory.

According to the Windows Resource Guide, you can restore the database by 
doing the following:

1) Quit Windows, delete REG.DAT, and then restart Windows.

2) Run Registration Info Editor (REGEDIT.EXE from the Windows 
directory--great icon), which  will display an empty list of registered 
file types.

3) Choose "Merge Registration File" from the File menu.

4) Select "SETUP.REG" (WINDOWS\SYSTEM directory) from the File 
Name list in the dialog box and click the OK button.

This will restore the original Windows Registration Database.

62. Why do all of  my sounds play fast?  It sounds like my card is one of 
the chipmunks.  How do I fix this?
It is likely you have a DMA conflict.  The following troubleshooting 
tips should help you figure out what is happening.  Remember, you 
cannot use the same DMA and IRQ for the Pro Audio Spectrum 16 and 
Sound Blaster emulation portions of the board.

Here is a sample line for your CONFIG.SYS: 

DEVICE=C:\PROAUDIO\MVSOUND.SYS  D:3  Q:7  S:1,220,1,5  M:0 T:1

Test the DMA and IRQ settings using PLAYFILE under DOS.

Reboot the system.  Make sure your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PROAUDIO).  Note that 
you may use something other than the TEST.WAV file to test your 
sound. ).  Test the sound by entering the following line:

PAS  RESET		[enter]
PLAYFILE  TEST.WAV	[enter]

You should hear the sound of a phone dialing.  If you hear no sound,
try another combination of DMA and IRQ values.

If the sound is okay, ensure the DMA you are using under 
Windows matches the DMA you are using under DOS.  Here is a copy of 
what your SYSTEM.INI file should look like as far as Media Vision 
drivers are concerned.  You should notice that the DMA setting is at the 
bottom of your SYSTEM.INI in the [mvproaud.drv] section.

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=3
irq=7

[opl3.drv]
drumchannel=10

63. My Pocket CD won't work.  I'm getting the error message,  "There is an 
undetectable problem in loading the specified device driver."
First, make sure you have a music CD in the drive before and when 
you launch PocketCD.  If not, you will get this error every time.

If you do have a music CD in the drive and still get the error, you will 
need to:

1) Go to the Control Panel (in Main).

2) Open DRIVERS, and look for [mci] CD Audio.  Double-click on this.

3) If you get a "One CD-ROM found" message, restart Windows, and try 
PocketCD again.  If there is no message, you will need to make sure your 
CD-ROM driver is loading in DOS.

4) You may need to delete and then reinstall the [mci] CD Audio driver.  
This is a Microsoft driver.  If you replace the [mci] CD Audio 
driver and PocketCD is still not working, you need to exit Windows and 
shut the system down.  Restart your system and try PocketCD one more 
time.

5)  Make sure you are using the proper version of MSCDEX for your 
system. MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a 
DOS version sensitive program.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure you are using the proper 
version of MSCDEX.EXE for your system.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

Here is a table to assist in determining the proper version of MSCDEX
for your system:

DOS version		MSCDEX.EXE version
==========================================
5.00			2.21
6.00			2.22
6.20			2.23

Finally, update your CD-ROM driver, (if available), since this can also 
create an error with PocketCD.

64. I'm unable to use the Media Player in Windows to play audio CDs.  
How can I correct this problem?
If you do not have an option for CD Audio with Media Player, then you 
will need to edit the MPLAYER.INI file for Windows.  You can use 
Notepad to edit the file.  Make sure you have the following line in 
the [Devices] section:

[Devices]
CDAudio=17,  CD Audio

65. I'm only getting sound from one channel when playing a music CD.
The only driver that affects CD Audio is the [mci] CD Audio driver.  This 
is a Windows driver.  It has no affect on the CD-ROM drive under DOS, 
so you should find out whether or not you are receiving stereo CD Audio 
while under DOS.  To test this, use the MUSICBOX.EXE  utility.  
MUSICBOX should be in your PROAUDIO directory.  

Start MUSICBOX.  Press "P" for Play.  You should hear 
CD-Audio.  You can press the <ESC> key to exit the program.  
The CD-ROM drive will continue to play the disc.  At your DOS 
prompt type the following command:

PAS  RESET	 [enter]

If you start hearing stereo sound, then your mixer was out of 
adjustment.

If your drive has a headphones jack, try plugging in a set of speakers or
headphones into the headphones jack on the CD-ROM drive.  If you still 
do not hear stereo, the drive is malfunctioning.

If you hear stereo out of the headphones jack, the problem is probably 
with the audio cable itself or its connection to the sound card.  Double 
check all of your connections. 

If you can determine that the audio cable is good, the sound card is 
going to be the source of the trouble.

If MUSICBOX works okay, you should check the Pocket Mixer in 
Windows.  If the Pocket Mixer is set properly, you should reinstall the 
[mci] CD Audio driver.  You will find the driver in the Drivers Applet 
under Control Panel.  Once you have replaced the [mci] CD Audio driver 
and  if the Windows CD player is still not working properly, you need to 
exit Windows and shut the system down.  Restart your system, and try the 
player one more time.

66. Is there a software developer's kit available for the 
Pro Audio Spectrum 16?
Yes, contact the Media Vision Sales department to purchase the 
SDK.  You can reach the Sales Department at 800-845-5870.

67. How do I get TBPro to work?  It used to work fine, but it doesn't 
work anymore.
Here are some trouble shooting tips that should allow you to use TBPro.  
Be aware that some of the versions of TBPro that Media Vision 
ships are 8-bit versions.

1)  Use an 8-bit DMA.  Here are some sample lines for your 
CONFIG.SYS and AUTOEXEC.BAT files:

CONFIG.SYS

DEVICE=C:\PROAUDIO\MVSOUND.SYS  D:3  Q:5  S:1,220,1,7  M:0 J:1

AUTOEXEC.BAT

SET BLASTER=A220  D1  I7  T3

2)  Use TBCONFIG.EXE to reconfigure TBPro.  Try reducing the 
sampling rate.  You might also try turning OFF the Graphics mode.

3)  Use the updated version of TBPro on the BBS.  This version 
supports 16-bit DMA's, and its filename is TBPRO.EXE

68. Can I connect other SCSI devices to the Pro Audio Spectrum?
Yes.  You need to purchase an ASPI driver from Adaptec.  Call 
the Adaptec Software Hotline at 1-(800)-442-SCSI , and request the 
the price of a product called SCSIworks!.   International customers will 
need to call (408)-945-8600 and ask for Pre-Sales.  You can also fax
your requests to:

(716)-873-0906
"Attn: Adaptec Order Desk"

After you install the correct driver from this product, you will have access 
to your SCSI device through the SCSI host adapter on the sound card.   
SCSIworks! supports SCSI hard drives, scanners, tape backup units, and 
many other SCSI devices.

69. I'm getting the following error message when I use RECFILE.  
"File is full or blocked." I am also not able to record 16 bit files.  
What is happening here?
This problem is caused by slow system throughput.  To correct this,
try the following:

1)  Reduce to a generic CONFIG.SYS and AUTOEXEC.BAT.

2)  Make sure your hard disk has been optimized (defragmented).  If 
you are using compression, such as Stacker, it is very likely 
you will not be able to record at the higher levels, 44khz, because it 
uses so much disk space.  You'll need about 10 megs of 
unfragmented disk space to record as the higher levels.
Compression utilities cause the disk to be fragmented, causing 
RECFILE not to work with the higher settings.

3)  Try a lower sampling rate or try recording to a ramdrive.

70. Why am I getting a GPF (General Protection Fault) in "user.exe" when 
I try to use Pocket Recorder?
If you are unable to record, you may have to "reset" the Pocket Recorder 
section of your WIN.INI file before the Pocket Recorder will work 
again.  Here is how you would "reset" the section.

1)  Edit the WIN.INI file.

2)  Find the section labeled:  [Media Vision Pocket Recorder]

3)  Highlight (select) the entire section with your mouse.  Make sure
you ONLY select the [Media Vision Pocket Recorder] section.

4)  Press the DELETE key.  This will remove the entire section.  

5)  Save the WIN.INI.

6)  Exit Windows.

7)  Restart Windows.  Try the Pocket Recorder.

